home *** CD-ROM | disk | FTP | other *** search
- Path: lrz-muenchen.de!sun2!ua302aa
- From: ua302aa@sun2.lrz-muenchen.de (Kurt Watzka)
- Newsgroups: comp.lang.c
- Subject: Re: A problem with fprintf
- Date: 9 Jan 1996 14:32:09 GMT
- Organization: Leibniz-Rechenzentrum, Muenchen (Germany)
- Distribution: world
- Message-ID: <4ctu99$96b@sparcserver.lrz-muenchen.de>
- References: <4cs8ie$5ru@no-names.nerdc.ufl.edu> <4csrrr$f06@gryphon.phoenix.net>
- NNTP-Posting-Host: sun2.lrz-muenchen.de
-
- brucew@phoenix.net (Bruce Wedding) writes:
-
- >vtigadi@cis.ufl.edu (Vishwajit Tigadi) wrote:
-
- >>I have a piece of code where the following statement fits in:
- >>
- >>fprintf(fp, "%s\n", src);
-
- >>signal SEGV (segmentation violation) in malloc at 0xef778634
- >>malloc+0x150: st %o0, [%l5]
-
- >Are you checking the return value of malloc()? Show us the code with
- >the malloc in it.
-
- He need not even know that there is a function called malloc(). The
- library can call library functions, too, and in this case we can
- suspect that there is a call to malloc() hidden in the implementation
- of fprintf().
-
- Kurt
- --
- | Kurt Watzka Phone : +49-89-2180-6254
- | watzka@stat.uni-muenchen.de
- | ua302aa@sunmail.lrz-muenchen.de
-